Creating and importing a message map

In the EDI Message Type form, you can export the schema files to use as a reference when customizing an EDI message map for the selected EDI message type.

To export the schema files:

  1. Open the Administration EDI Message Types Message Types view EDI Message Type form (on page 1).

  1. Click Export XSD File.

N4 displays the Export XSD File button for existing message types only. For a new EDI message type, you must add the message type before you can export the schema files.

  1. In the Export XSD File dialog box, select the location for the schema files and click Open.

When successful, N4 exports the baseMapping.xsd file and the appropriate schema file for the EDI class of the selected EDI message type, such as the activity.xsd file for an ACTIVITY EDI message.

 

You can edit a mapping file to receive and send data for unit flex fields in an EDI message. The following schema files support flex fields:

To create a new custom message map, you first need to export a standard data dictionary file and standard mapping file for editing.

To export a standard mapping file:

  1. In the Administration EDI Message Types Message Types view, double-click the standard EDI message type for the mapping file you want to export.

The EDI Message Type form opens.

  1. Open the Message Map tab EDI Message Map form (on page 1) for the standard or built-in message map.

  2. To export a custom or standard data dictionary file, click Export DIC.

  3. In the Export XML Configuration dialog box, specify a name for the data dictionary file and click Save.

To save an XML data dictionary file, you must enter a name and the extension (.dic).

To save a flat text dictionary file for a FLATFILE EDI message, you must enter a name and the extension (.fxd).

  1. To export a custom or standard mapping file, click Export MGT.

  2. In the Export XML Configuration dialog box, specify a name for the mapping file and click Save.

To save a mapping file, you must enter a name and the extension (.mgt).

  1. Edit and save the mapping file and data dictionary file as needed using the GoXML mapping utility.

If you edited a mapping file for a new message map, you need to add this new message map and then import your edited file(s). You cannot import an edited mapping file or data dictionary file for a standard or built-in EDI message map.

To add a message map and import a new custom mapping file:

  1. In the Administration EDI Message Types Message Types view, double-click the EDI message type for the message map you want to add.

The EDI Message Type form opens.

  1. In the Message Map tab add a new message map.

  2. Open the EDI Message Map form (on page 1) for the new message map.

  3. In the Map Id field, enter a name that uniquely identifies the EDI message map.

You can create multiple maps for an EDI message as trading partners may use different implementations of the EDI message.

  1. From the Direction list, select the direction of the EDI message.

  2. To import the data dictionary file that defines the EDI message structure, click Import DIC.

  3. In the Import XML Configuration dialog box, select the data dictionary file and click Open.

XML data dictionary files have the extension .dic and flat text dictionary files have the extension .fxd.

The EDI Message Map Dictionary File field displays --loaded-- in the text box to indicate that a data dictionary file is linked with the EDI message map.

  1. To import the mapping file that defines the EDI map, click Import MGT.

  2. In the Import XML Configuration dialog box, select the mapping file and click Open.

Mapping files have the extension .mgt.

The EDI Message Map File field displays --loaded-- in the text box to indicate that a mapping file is linked with the EDI message map.

  1. Optionally, in the Description field, enter a description of the map.

  2. Click Save.

If you are updating an existing custom message map, then you must export that message map's custom data dictionary and mapping file for editing. Once you've edited the mapping file, you need to import your edited file(s).

To import an updated custom mapping file:

  1. Open the Administration EDI Message Types Message Types view EDI Message Type form Message Map tab EDI Message Map form (on page 1) for the custom message map.

  1. If you edited the data dictionary file, to import your edited data dictionary file, click Import DIC.

If you do not import an edited data dictionary file, N4 uses the standard data dictionary file for the selected EDI message type, if available.

  1. In the Import XML Configuration dialog box, select the edited data dictionary file and click Open.

  2. To import the edited mapping file, click Import MGT.

  3. In the Import XML Configuration dialog box, select the edited mapping file and click Open.

  4. Click Save.

If you select a standard or built-in EDI message map, N4 does not display the Save button.